### Supported resource types

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/identity-server/5.11.0/docs/setup/promote-configurations.md`:
- Line 168: Replace the bold inline heading "**toolConfig.json**" with the
tab-style include label === "toolConfig.json" and ensure the following JSON
sample is written as a code block using the tab syntax: add a blank line after
=== "toolConfig.json" and start the JSON block with ```json while indenting the
JSON content by 4 spaces (so the code block content is tab-syntax compliant);
locate the literal "**toolConfig.json**" in the file to make this change.

---

Nitpick comments:
In `@en/includes/deploy/ctl-tool/logging.md`:
- Line 23: Update the description for the LOG_REQUEST_PAYLOADS property to use
active voice: replace "HTTP request bodies are logged at `DEBUG` level for POST
and PUT requests" with an active phrasing such as "logs HTTP request bodies at
`DEBUG` level for POST and PUT requests" while preserving the flag name
LOG_REQUEST_PAYLOADS and the behavior details (DEBUG level, POST and PUT).

In `@en/includes/deploy/ctl-tool/resource-specific-notes.md`:
- Line 3: Replace the verbose phrase "to be aware of when using" in the document
with a concise alternative such as "to note when using" or simply "when using";
locate the sentence that currently reads "The following notes describe
resource-type-specific behavior to be aware of when using IAM-CTL." and update
it to "The following notes describe resource-type-specific behavior to note when
using IAM-CTL." (or "when using IAM-CTL") to comply with the concise wording
guideline.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/includes/deploy/ctl-tool/resource-specific-notes.md`:
- Line 3: Change the passive sentence "The following notes describe
resource-type-specific behavior to be aware of when using IAM-CTL." to active
voice and present tense; replace it with "Note the following
resource-type-specific behavior when you use IAM-CTL." in the same paragraph
(look for the exact original string in resource-specific-notes.md and update
it).
- Line 6: Rewrite the paragraph to use active voice and present tense: change
"Users and groups are considered dynamic configurations" to "IAM-CTL treats
users and groups as dynamic configurations", replace "importing into a target
environment will remove this data from the affected resource" with "import
removes this data from the affected resource in the target environment", and
update the surrounding sentences so the actor ("IAM-CTL" or "import") performs
the actions (e.g., "IAM-CTL strips that data during export" → keep as active)
and the guidance lines remain clear about using IAM-CTL for initial creation,
adding dynamic configurations manually, and using EXCLUDE for future imports.
- Line 58: The sentence uses passive voice ("are stripped on export and are not
stored in the exported files"); rewrite it in active voice by making IAM-CTL the
subject. Replace that clause with an active formulation such as "IAM-CTL strips
these attributes on export and does not store them in the exported files,
because they are environment-specific and not portable," updating the line in
resource-specific-notes.md that currently reads "These attributes are stripped
on export and are not stored in the exported files, as they are
environment-specific and not portable."
- Line 42: Replace the undefined acronym and passive phrasing in the sentence
that starts with "When IAM-CTL creates organizations using M2M app credentials":
define M2M on first use as "machine-to-machine (M2M)" and convert to active
voice — e.g., "When IAM-CTL creates organizations using machine-to-machine (M2M)
app credentials, it does not assign any user as the creator, so no user has
access to the newly created organization; you can manually assign an
organization admin..." — keep the existing link text and target unchanged;
update the sentence in the resource-specific-notes content where "M2M" and the
passive clause appear.

---

Outside diff comments:
In `@en/includes/deploy/ctl-tool/resource-specific-notes.md`:
- Line 80: Rewrite the paragraph to use active voice and present tense: state
that "IAM-CTL does not export users included in approval steps" and that
"IAM-CTL removes those users from the exported workflow and removes any approval
steps that contain only users," and finish by clarifying that "import does not
restore those users or steps." Update the sentences replacing passive phrases
("are not exported by IAM-CTL", "will be removed from the exported workflow",
"will also be removed", "will be removed from the workflow on import") with the
active constructions above.
- Line 26: Rewrite the sentence to use active voice: replace "Group-based
password expiry rules of the password expiry connector are not exported by
IAM-CTL. As a result, these rules will be removed from the connector on import,
when **`ALLOW_DELETE`** is enabled." with an active formulation that names the
actor (IAM-CTL) and the action (does not export / removes), e.g. "IAM-CTL does
not export group-based password expiry rules from the password expiry connector,
so importing with **`ALLOW_DELETE`** enabled will remove those rules from the
connector." Ensure the revised sentence appears in resource-specific-notes.md
and retains the **`ALLOW_DELETE`** emphasis.
- Line 10: Change the passive sentence "Users and groups assigned to roles are
not exported or imported by IAM-CTL" to active voice in the file where that
sentence appears; specifically, update the line so the subject is "IAM-CTL"
(e.g., "IAM-CTL does not export or import users and groups assigned to roles")
to make the statement active and clearer.
- Line 18: The sentence "Excluding it will prevent new claim attribute mappings
of user stores from being propagated." uses an ambiguous pronoun and passive
voice; replace it with an explicit, active-voice sentence referencing the local
claim dialect text in the diff. For example, change that sentence to explicitly
name "the local claim dialect (http://wso2.org/claims)" and use active voice
such as "Excluding the local claim dialect (http://wso2.org/claims) prevents
propagation of new claim attribute mappings to user stores." Update the sentence
near "When propagating user stores, do not exclude the local claim dialect
(`http://wso2.org/claims`)." accordingly.
- Line 22: The sentence "Excluding roles will prevent new application roles from
being propagated." uses passive voice; update the line in
resource-specific-notes.md (the sentence starting with "Excluding roles will
prevent...") to active voice—for example: "Excluding roles prevents us from
propagating new application roles." Replace the original sentence with this
active-voice version (or an equivalent active construction) to comply with the
style guideline.
- Line 32: Rewrite the passive sentence so the subject performs the action:
replace "Outbound provisioning groups of outbound provisioning connectors are
not exported by IAM-CTL. As a result, these groups will be removed from the
identity provider on import." with an active-voice sentence that names IAM-CTL
as the actor and describes the consequence, e.g. start with "IAM-CTL does not
export outbound provisioning groups of outbound provisioning connectors, so
importing removes these groups from the identity provider." Update the sentence
containing "Outbound provisioning groups of outbound provisioning connectors",
"IAM-CTL", and "identity provider on import".

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@en/includes/deploy/ctl-tool/resource-specific-notes.md`:
- Line 80: Rewrite the passive sentence so IAM-CTL is the subject and use active
present tense: change "Users included in approval steps are not exported by
IAM-CTL. These users will be removed from the exported workflow, and any
approval steps that contained only users will also be removed. As a result,
these users and steps will be removed from the workflow on import." to an active
construction that starts with "IAM-CTL" (for example: "IAM-CTL does not export
users included in approval steps; it removes those users from the exported
workflow and also removes any approval steps that contain only users, so they
are removed on import."), ensuring present tense and direct voice throughout.
- Line 46: Replace the word "Alternatively" at the start of the sentence about
assigning a creator with a more concise connector (e.g., "To assign a creator at
import time, configure ...") so the line reads succinctly and still references
CREATOR_ID and CREATOR_USERNAME under ORGANIZATIONS in toolConfig.json; update
the string in resource-specific-notes.md where that sentence occurs to use the
shorter phrasing while keeping the same configuration keys and file name.
- Line 32: Change the passive sentence "Outbound provisioning groups of outbound
provisioning connectors are not exported by IAM-CTL. As a result, these groups
will be removed from the identity provider on import." to active voice with
IAM-CTL as the subject; for example, replace it with a single active sentence
such as "IAM-CTL does not export outbound provisioning groups of outbound
provisioning connectors, so importing will remove these groups from the identity
provider." Update the line in resource-specific-notes.md where that sentence
appears.
- Line 10: Change the passive sentence "Users and groups assigned to roles are
not exported or imported by IAM-CTL." to active voice with IAM-CTL as the
subject; replace it with a direct statement such as "IAM-CTL does not export or
import users and groups assigned to roles." Ensure the updated text is applied
where the current sentence appears in resource-specific-notes.md and preserves
the original meaning and tense.
- Line 26: Rewrite the sentence to use active voice with IAM-CTL as the subject:
change "Group-based password expiry rules of the password expiry connector are
not exported by IAM-CTL. As a result, these rules will be removed from the
connector on import, when **`ALLOW_DELETE`** is enabled." to a direct active
construction mentioning "IAM-CTL" and "**`ALLOW_DELETE`**" (for example:
"IAM-CTL does not export group-based password expiry rules from the password
expiry connector; when **`ALLOW_DELETE`** is enabled, IAM-CTL will remove these
rules on import."). Ensure the phrase "password expiry connector", "group-based
password expiry rules", "IAM-CTL", and "**`ALLOW_DELETE`**" remain present and
the tense is present.